Windows speech recognition – Lost ability to use "caps" function in windows 7
I’ve been using windows speech recognition exclusively instead of typing for over three years. I just upgraded from vista to windows 7 and from Microsoft office 2007 to office 2010. All in all I believe that windows speech recognition works better than ever with one exception. The “caps” function is horrible. In the past I would speak and WSR would take dictation. Of course it did not know when I wanted certain words capitalized. So when I would get to the end of a paragraphs or a page I would go back to the beginning and tell it what words I wanted to be capitalized by saying the word “caps” and then saying the word or words (as long as they were in sequence) that I wanted capitalized. Or I could say the word “select” and then say the sequence of words that I wanted capitalized, and then say either “caps” or “caps that” and it would capitalize the first letter of each of the words that were selected. Please advise. Thank you. Mindy Scott
February 2nd, 2011 4:11am

Capitalize the first letter of the word Caps word Capitalize all the letters of the word All caps word Make all the letters in the word lowercase No caps word Change the next number of words to uppercase Change next 10 words to uppercase Change the next number of words to lowercase Change next 10 words to lowercase Hope this helps.
Free Windows Admin Tool Kit Click here and download it now
February 3rd, 2011 12:05am

Timothy McCormack leo HuangLijun Thanks Tim, but unfortunately this did not help at all. The “all caps” function works properly in all scenarios. If I say “all caps word”, that word is typed next with all caps. If I say “Change next 10 words to uppercase”, it does just that. If I’ve already written a paragraph or a page and I want a string of words to all contain all caps, I say “all caps” and then the string of words and those words are changed to contain all caps. This works regardless of where my cursor is positioned on the page. Same with the “no caps” function. If I say “no caps word” the next word is typed with no caps. If I say “Change next 10 words to lowercase”, it performs the function correctly. If I’ve already written a paragraph or a page and I want a string of already typed words to contain no caps, I just say “no caps” and then the string of words and the string of words are converted, with the exception of the first word of the sentence, to contain no caps. Not so with the “caps” function. WSR automatically capitalize the first word of every sentence. If you want a word capitalized in the middle of a sentence, you have to capitalize it as you get to it. You can say “caps” and then the word and the next word typed will begin with a capital letter. The problem exists when I try to capitalize words that have already been typed. I used to be able to insert my cursor within a word and say either “caps” or “caps that”. WSR would capitalize the word my cursor was in. Saying “caps” in this case no longer changes the first letter of the word to a capital letter. Saying the words “caps that” while your cursor is inserted in a word turns on the Caps Lock on the keyboard. But then, if you say “undo that” it does not turn the Caps Lock off. With my cursor anywhere on the page I used to be able to say “caps” and then say a string of words and if there was only one instance of those words visible on the page each one of the words would be capitalized. If there were more than one instance of this same group of words, WSR would prompt me with numbers that I had to choose from at each instance. Once I chose the number of the instance I wanted to capitalize I would say “OK” and the first letter of each word in that group would be capitalized. Instead of doing this now, it types these words wherever the cursor is located and capitalizes only the first word of the group. I have changed two things on the computer I am having this problem with. I upgraded from Vista to Windows 7 and from Office 2007 to Office 2010. Everything else seems to be working perfectly, but this is extremely frustrating. Looking forward to an answer. Mindy /Mindy Scott/
February 10th, 2011 11:46pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics